2020R2.4 Resolved Issues

The 2020 R2.4 version will be deployed on June 6. This minor release will address some high priority customer bugs and update the UA version.

ECL-11308 – Unable to remove predecessors/resources from task worksheet in Upland Project Planner.

UPP provides a quick method of editing predecessors/resources by entering text directly on the worksheet. We have identified and fixed a bug that prevented users from clearing the predecessors/resources field.

ECL-11448 – Use Eclipse timeout inside Upland Project Planner.

Eclipse has a timeout provider function that allows users to specify a custom timeout. UPP has been enhanced to use the same provider so that timeouts will occur at the same time.

ECL-11461 – Upland Analytics returns incorrect results when using “Count Distinct” as a custom field.

When building a chart using a “Count Distinct” custom field, many rows were eliminated from the data set by an incorrectly built database join query. The “Count Distinct” operator would be used, for example, when building a pie chart to count risks by status.

ECL-11467 – Help Index Updates

The online help links from Eclipse are now context-sensitive, meaning that a user who accesses the help directly from Eclipse will be redirected to a specific help page.

ECL-11479 – Permission incorrectly applied to Upland Analytics views.

Permissions were applied incorrectly to several UA views which resulted in users not being allowed to see any data. This problem has been fixed.

ECL-11486 – Adding task comments using the API throws an error.

When working with task comments via the API, and providing a valid comment to the POST/PUT endpoints, users would receive an error stating “Comment is required.”.

ECL-11491 – API – Unable to set “Task Category” for tasks where value already exists.

When working with the API directly to update the “Task Category” field, the update was not saving properly. Users were required to clear the “Task Category” before changing it to a new one. This problem has been resolved.

ECL-11492 – API – Unable to log time entries on behalf of another user.

When building integrations that exchange time entries between multiple systems like JIRA + ECLIPSE, the endpoint needed to support impersonation so that the API user can log time on behalf of any other resource.

ECL-11514 – Error when submitting a project request with multi-select custom properties.

When confirming a project request based on a project template that has multi-select custom properties, users would receive an error stating: “Submitted request had invalid properties that could not be applied to created project.”. The error has been resolved and projects are now created successfully.

ECL-11519 – Report Preferences loaded incorrectly on “Resource Extract Report”.

When executing any canned report, Eclipse will remember your last preference to be used next time. In the “Resource Extract Report”, there was a scenario where the “Resources” preference was saved incorrectly and caused problems executing the report.

ECL-11520 – Report Preferences not loading dates correctly.

In several reports with date filters, the report preferences were not loading correctly. Dates would be shifted on subsequent runs of the following reports: User Login Report, Project Activity Report, Project Timesheet Report, Resource Extract Report, Resource Histogram Report, Resource Time Report, Resource Timesheet Report, Timesheet Compliance Report, Timesheet Note Summary Report.

ECL-11560 – Schedule save fails due to “arithmetic overflow” error.

One of the Eclipse database tables was using a “bigint” to store id’s. During a test integration that ran many insert/deletes, we exceeded the maximum allowed value and have updated the data type accordingly. This change has no effect on existing data.